Subject: Proposed Changes to "CPIC use of Distributed Directory"

From: "Mel Jones (Tie: 444-4363)" <[email-masked]>
Date: Mon, 1 Nov 93 10:39:42 EST

- support for incomplete DN
          - specification of object ID for OSI

All:

The existing 10/22 AP proposal for "CPIC Use of Distributed Directory"
does not address the capability of specifying 1) an incomplete
distinguished name or 2) an object_ID to identify the partner program for
OSI.  As I mentioned in my 10/22 note, Jeff Hildebrand and I have been
discussing these topics (see his note dated 10/18/93 for background) and
have come up with a set of proposed changes.  The attached text discusses
background of the new requirements, then gives sample text changes for
the existing (10/22) AP-level document.

Please send comments on this proposal, as well as comments on the latest
draft of the AP proposal, by this Friday, 11/5.  If we can reach
consensus for AP, my goal is to distribute a new updated version of the
proposal by 11/12.

Regards,
Mel

- - - - - - begin proposal text - - - - - - - - - - - - -

**  The discussion below assumes understanding/knowledge of
**  background info presented in part 1 of the AP document.

Discussion of Requirements
- - - - - - - - - - - - -
The existing proposal allows three forms of the partner_ID:
  - DN (a complete DN)
  - PFID (a functional identifier)
  - program binding (explicit destination information)

Two additional ways of identifying the program are proposed:  1)
a partial DN and 2) an object identifier for OSI.  These are
discussed below.

Partial DN
- - - - - -
The partial DN is useful because it allows a program to specify
an identifier for its partner without knowledge of the complete
directory information tree.  For example, the complete DN might be

      /C=US/o=UNC/OU=ChapelHill/CommonName=ThomasWolfe

A partial DN would be /CommonName=ThomasWolfe/.  Use of a partial
DN removes the need for program knowledge of the complete
directory tree.  The directory object is retrieved by using the
partial DN in conjunction with a default local prefix.  The local
system calculates the complete DN by appending the prefix to the
front of the partial name.

Object Identifier for OSI
- - - - - - - - - - - - -
In OSI, universally used programs are sometimes identified with
registery-specified object identifiers.  The OID is used as an
attribute_value for the attribute_type of TPSU_Title.  For
example, a program in the aerospace industry that allows a
program to order engine parts might be registered with an OID of
1.22.33.44.55.  The same program might exist in multiple
companies (each with a different set of destination information).
In this example, the requirement is to search the
directory for all directory objects containing an attribute with
attribute_type=TPSU_Title and attribute_value=1.22.33.44.55.

Proposed Solution
- - - - - - - - -
The proposed solution is to add two new values to the
partner_ID_type parameter.  The modified text for partner_ID_type
(changes from 10/22 draft marked with :) is shown below.

PARTNER_ID_TYPE (input)
- - - - - - - - - - - -
Specifies the type of the partner_ID that will be used on this
conversation.

The partner_ID_type variable can have one of the following values:

o   CM_DISTINGUISHED_NAME
: The partner_ID variable contains a complete distinguished name.   CPI
| Communications will use the complete DN to retrieve destination
information from a distributed directory.

: o   CM_LOCAL_DISTINGUISHED_NAME
: The partner_ID variable contains a local distinguished name.  When
: combined with a system-specific prefix, the local DN creates a complete
: DN for access of destination information from a distributed directory.

o   CM_PROGRAM_FUNCTION_ID
The partner_ID variable contains a program function identifier that CPI
Communications can use to search the distributed directory and obtain
the partner binding.

: o   CM_OSI_TPSU_TITLE_OID
: The partner_ID variable contains an object identifier for an OSI TPSU
: title.  On systems supporting attribute_type searchs, CPI
: Communications will search the directory for objects containing
: attributes with an attribute_type of TPSU_ENTRY and an attribute_value
: equal to the specified partner_ID.

o   CM_PROGRAM_BINDING
The partner_ID variable contains a program binding for the partner
program.  For more information on the format of a program binding, see
"Program Binding" on page 50.

- - - - - - - - - - end of change text - - - - - - - - - - - - - - - -